ci: move actions off deprecated Node 20 - #21
Merged
Conversation
added 2 commits
August 2, 2026 18:52
GitHub is already force-running checkout, cache and action-gh-release on Node 24 and warns on every run. Bump to the current majors, which target node24 natively, before the forcing is removed and releases break. action-gh-release v3 keeps every input this workflow uses.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every workflow run currently emits:
GitHub is already forcing these onto Node 24. Bump to the current majors, which target
node24natively, before the forcing is removed and releases break.actions/checkoutv4 -> v7.0.1actions/cachev4 -> v6.1.0softprops/action-gh-releasev2.6.2 -> v3.0.2All remain pinned to full commit SHAs, since the release job imports the Developer ID signing key.
Checked
action-gh-release@v3'saction.ymlbefore bumping: it declaresusing: node24and still supports every input this workflow passes (tag_name,files,body_path,fail_on_unmatched_files). The release job is only exercised on tag push, so this one could not be validated by CI and was verified by reading the action definition instead.